home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group03a.txt
/
000005_icon-group-sender_Wed Feb 5 08:08:10 2003.msg
< prev
next >
Wrap
Internet Message Format
|
2003-12-22
|
2KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.11.1/8.11.1) id h15F6rO01384
for icon-group-addresses; Wed, 5 Feb 2003 08:06:53 -0700 (MST)
Message-Id: <200302051506.h15F6rO01384@baskerville.CS.Arizona.EDU>
Date: Tue, 4 Feb 2003 20:41:03 -0700
From: Clint Jeffery <jeffery@cs.nmsu.edu>
To: lhota.adarose@verizon.net
CC: unicon-group@lists.sourceforge.net, icon-group@cs.arizona.edu
Subject: Re: [Unicon-group] wincap legal status (!)
Errors-To: icon-group-errors@cs.arizona.edu
Status: RO
[Frank has recently voiced his support for removing wincap from the
Icon and Unicon source code bases.]
One piece of information I'll add to Frank's comments is: Icon and Unicon
use a tiny part of the wincap subdirectory, just the .bmp reading and
writing code. The Icon and Unicon sources do include a makefile sufficient
for building the wincap object files necessary to build Icon/Unicon on
MSVC++ 6.0, but Frank's observation is correct that the makefile rules for
building a working executable wincap demo are out of date and VC++ is not
backward compatible to the extent needed to build the executables.
I searched on the net and found several pages that purported to document
the .bmp format, and some non-wincap sample code, but haven't seen something
that explicitly placed itself in the public domain or under an open source
license. To get rid of wincap, we need free .bmp read/writing code, or else
we need to write our own. From the specs, it appears .bmp is an "easy"
format, so if someone wants to write the code for it, it will be pretty
easy for us to get rid of wincap. If anyone wants to help with this, I am
all in favor of Frank's suggestion.
Wincap does have some other capabilities that would be nice to add
to the Windows versions of Icon and Unicon, like the ability to print
images, but we aren't making use of them at present.
Clint jeffery@cs.nmsu.edu